Add a test for various cases of invalid macro definitions.

Closes: rust-lang#143351

This removes special-casing of boxes from `rustc_pattern_analysis`, as a
first step in replacing `box_patterns` with `deref_patterns`.
Incidentally, it fixes a bug caused by box patterns being represented as
structs rather than pointers, where `exhaustive_patterns` could generate
spurious `unreachable_patterns` lints on arms required for
exhaustiveness; following the lint's advice would result in an error.

A blocking implementation of tcp4 write.

Signed-off-by: Ayush Singh <ayush@beagleboard.org>

std: sys: net: uefi: tcp4: Implement write

A blocking implementation of tcp4 write.

…ser, r=jdonszelmann

Port `#[non_exhaustive]` to the new attribute parsing infrastructure

Ports `non_exhaustive` to the new attribute parsing infrastructure for rust-lang#131229 (comment)

r? ``@jdonszelmann``

…nkov

Remove names_imported_by_glob_use query.

Based on rust-lang#143247
r? ``@ghost`` for perf

…errors

Assign dependency bump PRs to me

These PRs sometimes get lost as GH reduces their visibility, so I wanted to get an assignment so I can help these PRs land

…r=compiler-errors

Remove some unnecessary `unsafe` in VecCache

I'm pretty sure, but until perf confirms,
r? ghost

…piler-errors

mbe: Gracefully handle macro rules that end after `=>`

Add a test for various cases of invalid macro definitions.

Closes: rust-lang#143351

…adrieril

remove special-casing of boxes from match exhaustiveness/usefulness analysis

As a first step in replacing `box_patterns` with `deref_patterns`, this treats box patterns as deref patterns in the THIR and exhaustiveness analysis. This allows a bunch of special-casing to be removed. The emitted MIR is unchanged.

Incidentally, this fixes a bug caused by box patterns being treated like structs rather than pointers, where enabling `exhaustive_patterns` (rust-lang#51085) could give rise to spurious `unreachable_patterns` lints on arms required for exhaustiveness. Following the lint's advice to remove the match arm would result in an error. I'm not sure what the current state of `exhaustive_patterns` is with regard to reference/box opsem, or whether there's any intention to have `unreachable_patterns` be more granular than the whole arm, but regardless this should hopefully make them easier to handle consistently.

Tracking issue for deref patterns: rust-lang#87121

r? `@Nadrieril`

clean up GVN TypeId test

addresses rust-lang#142789 (comment)

This is an attempt to clarify what this test is actually supposed to test and make it less dependent on `TypeId` internals (it now depends on the output of `type_name` instead).

I verified that this version still miscompiles on `nightly-2025-02-11`.

r? ``@oli-obk`` ``@RalfJung``